<html>
<head>
<link rel="stylesheet" href="docstyle.css" type="text/css">
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<link rel="Start" href="index.html">
<link title="Index of types" rel=Appendix href="index_types.html">
<link title="Index of exceptions" rel=Appendix href="index_exceptions.html">
<link title="Index of values" rel=Appendix href="index_values.html">
<link title="Index of modules" rel=Appendix href="index_modules.html">
<link title="Jvm_bytecode" rel="Chapter" href="Jvm_bytecode.html">
<link title="Jvm_io" rel="Chapter" href="Jvm_io.html">
<link title="Jvm_jar" rel="Chapter" href="Jvm_jar.html">
<link title="Jvm_type" rel="Chapter" href="Jvm_type.html"><title>HaXeJvm Documentation : Index of types</title>
</head>
<body>
<center><h1>Index of types</h1></center>
<table>
<tr><td align="left"><br>A</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEaccess_flag">access_flag</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEattribute_info">attribute_info</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td><div class="info">
Attributes are a flexible datastructure and provide means to annotate classes, methods, fields and even attributes themselves
 with metadata.
</div>
</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEatype">atype</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
<tr><td align="left"><br>C</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEcode_attr_info">code_attr_info</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td><div class="info">
this attribute holds the meat of a method, its buisness logic in form of a sequence of opcodes.
</div>
</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEcp_info">cp_info</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td><div class="info">
This is a structered representation of data storable in the constant pool.
</div>
</td></tr>
<tr><td align="left"><br>E</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEexception_table">exception_table</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
<tr><td align="left"><br>F</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEfield_info">field_info</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
<tr><td align="left"><br>G</td></tr>
<tr><td><a href="Jvm_type.html#TYPEgeneric_opcode">generic_opcode</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
Jvm opcode families.
</div>
</td></tr>
<tr><td align="left"><br>I</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEinner_class">inner_class</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_type.html#TYPEintercodes">intercodes</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td></td></tr>
<tr><td align="left"><br>J</td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_annotation">jvm_annotation</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_class">jvm_class</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
This type is supposed to represent a data structure ,that is easily transformable to a class file 
 or set of class files, while bridging the gap, between haXe classes and jvm classes.
</div>
</td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_construct">jvm_construct</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_enum">jvm_enum</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
It is unclear as of now, if such a datastructure is necessary, but we keep it around to remind ourselves of its existence from time to time
</div>
</td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_field">jvm_field</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
in contrast to haXe, a jvm makes a clear distinction between a field and a method (function).
</div>
</td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_interface">jvm_interface</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
At this point it is still undecided how to implement haXe enums on a jvm, but in all likelyhood it will
 heavily depend on the haXe "switch" keyword conversion, and will be optimized for performance.
</div>
</td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_method">jvm_method</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
A method is a function associated with a class.
</div>
</td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_params">jvm_params</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_path">jvm_path</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_property">jvm_property</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
A data field with optional getter and setter methods.
</div>
</td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_reference">jvm_reference</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_scope">jvm_scope</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td></td></tr>
<tr><td><a href="Jvm_type.html#TYPEjvm_type_type">jvm_type_type</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
This might be an unfortunate name, but I currently do not know a better 
 word for the group, where classes, interfaces and the likes belong to   
 ...
</div>
</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEjvm_version">jvm_version</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td><div class="info">
Although, in theory, compiling against lower versions should always result in bytecode executable by the newest JVMs, for 
 performance, and feature reasons, we want to be very aware of our target version.
</div>
</td></tr>
<tr><td align="left"><br>L</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPElocal_var">local_var</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
<tr><td align="left"><br>M</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEmethod_info">method_info</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
<tr><td align="left"><br>O</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEopcode">opcode</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td><div class="info">
JVM instruction set.
</div>
</td></tr>
<tr><td align="left"><br>S</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEstackmap_frame">stackmap_frame</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td><div class="info">
a stackmap frame represents the type state of local variables and     
 opstack for any given opcode.
</div>
</td></tr>
<tr><td><a href="Jvm_io.html#TYPEstream">stream</a> [<a href="Jvm_io.html">Jvm_io</a>]</td>
<td></td></tr>
<tr><td align="left"><br>T</td></tr>
<tr><td><a href="Jvm_type.html#TYPEt">t</a> [<a href="Jvm_type.html">Jvm_type</a>]</td>
<td><div class="info">
Types for the jvm oprand stack, constant pool etc.
</div>
</td></tr>
<tr><td><a href="Jvm_io.html#TYPEt">t</a> [<a href="Jvm_io.html">Jvm_io</a>]</td>
<td><div class="info">
jvm bytecode types -&gt; types for the jvm class file format Note: the     
 signed byte types are as far as I can see only used for switch opcodes, 
 but even there not really necessary, I leave them nonetheless for       
 potential future use or backward compatability, in case someone         
 implements it ^^
</div>
</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEt">t</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td><div class="info">
jvm class file format is identifaiable through magic number 0xCAFEBABE
</div>
</td></tr>
<tr><td align="left"><br>V</td></tr>
<tr><td><a href="Jvm_bytecode.html#TYPEverification_type_info">verification_type_info</a> [<a href="Jvm_bytecode.html">Jvm_bytecode</a>]</td>
<td></td></tr>
</table><br>
</body>
</html>